Omit x, y coordinates, x & y bounds from conversion #330
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
veenstrajelmer
approved these changes
Feb 24, 2025
There was a problem hiding this comment.
Tested with:
import xarray as xr
import xugrid as xu
file_nc = r'P:\archivedprojects\11206304-futuremares-rawdata-preps\data\CMIP6_BC\CMCC-ESM2\uo_Omon_CMCC-ESM2_historical_r1i1p1f1_gn_199001-200912.nc'
ds = xr.open_mfdataset(file_nc, chunks={'time':1})
topology = {"mesh2d":{"x":'i',
"y":'j',
"x_bounds":'vertices_longitude',
"y_bounds":'vertices_latitude',
}
}
uds = xu.UgridDataset.from_structured2d(ds, topology=topology)
print(uds.coords)
print(uds.data_vars)
assert set(uds.coords) == set(['longitude', 'latitude', 'lev', 'mesh2d_nFaces', 'time'])
assert set(uds.data_vars) == set(['lev_bnds', 'time_bnds', 'uo'])This now results in the expected coords/data_vars (and also dims)
19 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
X and Y coords aren't relevant; they're stored in the Ugrid topology.
In particular, the original bounds might be somewhat messy (e.g. the triangle stuff...). If a user want the coordinates, they can use https://deltares.github.io/xugrid/api/xugrid.UgridDatasetAccessor.assign_face_coords.html
Which are nice and consistent (i.e. counterclockwise, and without repeated vertices).